Skip to content

ci: build on Node 26 - #27

Merged
diecodev merged 1 commit into
v2from
ci/node-26
Oct 30, 2026
Merged

diecodev merged 1 commit into
v2from
ci/node-26

Conversation

@diecodev

Copy link
Copy Markdown
Owner

Moves the CI, the release and the website deploys from Node 24 to Node 26.

Why

Production deploys don't build on Vercel: website.yml runs vercel build on the GitHub runner, then vercel deploy --prebuilt. That runner used Node 24, from .github/actions/setup, so production was recorded with 24 while Vercel's default (and the previews it builds itself) is 26.

Vercel attributes the version to package.json. The root engines.node is the range >=22.x, which accepts 24.

With this change, the CI, the release, production deploys, previews and local development all run on Node 26. Vite 8 (^20.19.0 || >=22.12.0) and Qwik rc.4 (^20.3.0 || >=21.0.0) both support it.

What changes

  • .github/actions/setup/action.yml: Node 26. It's used by the CI, the release's stage job and the website deploy.
  • release.yml: the github_release job (changelogithub) also uses 26.

The root engines.node stays >=22.x. It's the published library's package.json, so pinning it to 26.x would force Node 26 on anyone who installs qwik-sonner.

The CI of this PR runs on Node 26 and checks the change.

The CI, the release and the website deploys ran on Node 24, while Vercel's previews (and its default) use Node 26, as does local development. Production deploys build with `vercel build` on the runner, so they were recorded with Node 24 instead of the project's 26.
@vercel

vercel Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
qwik-sonner Ignored Ignored Preview Oct 30, 2026 4:30am UTC

@diecodev
diecodev merged commit 7ba1551 into v2 Oct 30, 2026
5 checks passed
@diecodev
diecodev deleted the ci/node-26 branch October 30, 2026 04:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant